Enrich Candidate Step Now Correctly Writes to Submission Fields
Automations
Amplify Customers Only
An issue was resolved where the Enrich Candidate step in Submission-based automations displayed submission fields but incorrectly wrote enrichment data to candidate fields instead, which caused data to be stored on the wrong record type.
Why does it matter?
The Enrich Candidate step now correctly writes results to submission fields when selected in Submission-based automations. This fix ensures data integrity by storing enrichment information on the appropriate record, improving accuracy for workflows that rely on submission-level data.This is part of the BHA 2025.12.1 release. Click here for release calendar details.
Was this helpful?